Pin npm to 11.x to fix release publish (sigstore bundling bug)#1237
Merged
Conversation
|
commit: |
taranvohra
approved these changes
Jul 9, 2026
gregberge
approved these changes
Jul 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The
Releasejob fails atchangeset publishwithnpm error Cannot find module 'sigstore'(fromlibnpmpublish/lib/provenance.js).npm 12.0.0 (released 2026-07-08) ships without the bundled
sigstoremodule thatlibnpmpublishrequires to generate provenance. The workflow rannpm install -g npm@latest, picking up the broken 12.0.0, so publishing withNPM_CONFIG_PROVENANCE: truecrashes. Upstream: npm/cli#9722.The crash happens before any package is pushed, so
@gitbook/api@0.187.0(bumped by #1236) never reached npm.